Skip to content

Resolve reports snapshot-first in Search bulk Delete and Reject - #99047

Merged
mountiny merged 14 commits into
Expensify:mainfrom
callstack-internal:VikckyStash/bugfix/98985-harden-bulk-rules
Sep 8, 2026
Merged

mountiny merged 14 commits into
Expensify:mainfrom
callstack-internal:VikckyStash/bugfix/98985-harden-bulk-rules

Conversation

@VickyStash

@VickyStash VickyStash commented Aug 20, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

Follow-up to the Search Pay fix (#98760 / #98444): the audit of the other Search bulk actions found two remaining paths that read the report from the Onyx report_ collection only — a collection populated only for reports the user has already opened. The search snapshot always contains the matched expense reports, so both paths degraded silently for reports visible in search results but never opened.

Bulk Delete (src/hooks/useSearchBulkActions.ts): both deleteAppReport call sites looked the report up in Onyx only. When the report wasn't cached, deleteAppReport bailed out early and the selected row was silently skipped. Both call sites now resolve the report via getReportFromSearchSnapshot(reportID, searchData, allReports).

Fixed Issues

$ #98985
PROPOSAL: N/A

Tests

  • Verify that no errors appear in the JS console

Evicting the report from Onyx in the dev console:

Onyx.set('report_<reportID>', null)

Delete:

  1. Make sure a target expense report appears on the Spend > Reports tab.
  2. Evict it from Onyx (see above).
  3. Select that report's row and run bulk Delete, confirming the modal.
  4. See the report has been deleted.

Offline tests

Same, as in Tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

  • Verify that no errors appear in the JS console

Same, as in Tests

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

MacOS: Chrome / Safari
delete.mp4

@codecov

codecov Bot commented Aug 20, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/libs/actions/Search.ts 54.29% <71.42%> (+0.49%) ⬆️
src/hooks/useSearchBulkActions.ts 71.81% <60.00%> (+0.79%) ⬆️
... and 10 files with indirect coverage changes

@VickyStash
VickyStash marked this pull request as ready for review August 20, 2026 10:43
@VickyStash
VickyStash requested review from a team as code owners August 20, 2026 10:43
@melvin-bot
melvin-bot Bot requested review from heyjennahay and shubham1206agra and removed request for a team August 20, 2026 10:43
@melvin-bot

melvin-bot Bot commented Aug 20, 2026

Copy link
Copy Markdown

@shubham1206agra Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team August 20, 2026 10:43

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d57514a31b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts Resolved
@VickyStash

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 401adaa0dc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/Search.ts Outdated
}

const key = `${ONYXKEYS.COLLECTION.REPORT_ACTIONS}${reportID}` as const;
return allReportActions?.[key] ?? searchData?.[key];

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Merge live and snapshot actions before deleting

When live Onyx contains only part of a report's actions—for example after an incremental load or action push—this whole-map ?? discards every action available only in the search snapshot. deleteAppReport iterates the returned map to populate transactionIDToReportActionAndThreadData and optimistically unreport expenses, so those missing CREATE actions leave transactions attached to the deleted report, particularly while offline. Merge the snapshot and live maps with live entries winning per action ID. Fresh evidence beyond the previous thread is that this new helper selects a non-null live dictionary wholesale rather than combining it with the snapshot.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codex, does it make sense just prioritize snapshot actions then?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Codex Review: Didn't find any major issues. Bravo.

Reviewed commit: 401adaa0dc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kept as is, added a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@VickyStash I am not sure about keeping this as it is. @mountiny What's your take here?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So what I'm thinking is that maybe we shouldn't use snapshot report actions in this case at all.

@VickyStash This might backfire when live report action is not present for an expense for some reason. But I think we should be consistent here for getReportActionsFromSearchSnapshot and getReportFromSearchSnapshot.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might backfire when live report action is not present for an expense for some reason.

BE should return the correct info in the delete response then, right?

But I think we should be consistent here for getReportActionsFromSearchSnapshot and getReportFromSearchSnapshot.

So, returning snapshot result and falling back to live?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, returning snapshot result and falling back to live?

Yes, but I would like to hear @mountiny's opinion.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hard to judge what will be better, I guess there could be edge cases in both directions. I agree with where you landed though

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

returning snapshot result and falling back to live

On my way to apply this, then!

@mountiny

Copy link
Copy Markdown
Contributor

@MelvinBot review
@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: cfdbbe86e7

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/libs/actions/Search.ts Resolved
@MelvinBot

Copy link
Copy Markdown
Contributor

Review

Solid, well-scoped follow-up. The core change is correct: both Bulk Delete call sites and Bulk Reject now resolve the report snapshot-first via getReportFromSearchSnapshot, and the new getReportActionsFromSearchSnapshot gives deleteAppReport the report actions it needs even for never-opened reports (the snapshot type does carry reportActions_ entries). The rejectMoneyRequestsOnSearch object-param refactor is complete — the single caller was updated, and both dependency arrays now include the snapshot (searchResults?.data / currentSearchResults?.data). The audit was accurate too: the Export/Mark-as-exported paths already have snapshot fallbacks, so Delete and Reject really were the remaining gaps.

A few things to confirm — none blocking:

1. Reject now reads transactionCount / policyID from the snapshot for cached reports too, not just uncached ones. Previously the reject loop read allReports (live-only); it now prefers the snapshot whenever present. For a report the user has opened and mutated locally after the search snapshot was taken, report?.transactionCount can now be the stale snapshot value, which feeds effectiveTransactionCount → areAllExpensesSelected → whether the delayed-submission whole-report path (rejectMoneyRequestInBulk) is chosen vs one-by-one. That's the intended trade-off for consistency with what the user selected on the search page, but worth a sanity check that a stale snapshot count can't misroute a cached report.

2. No unit tests for the new fallback branches. Codecov shows a coverage drop on both files and the diff touches no test files, though the checklist marks "added unit tests." tests/unit/hooks/useSearchBulkActionsDeleteTest.ts already exists — extending it with an evicted-report case (Onyx.set('report_<id>', null) → run bulk delete → assert deleteAppReport still receives the report + reportActions from the snapshot) would lock in exactly the regression this PR fixes.

3. Same-class pattern nearby, out of scope but worth a follow-up. In areAllTransactionsFromDMReports, the iouReport resolves from search data with a fallback, but the chat report at line 1610 is looked up live-only (allReports?.[...]). For an uncached chat report that would yield isDM(undefined) === false. Pre-existing and not part of this PR, but since this PR is the audit for exactly this class, flagging it for a potential follow-up.

Minor: the report is resolved snapshot-first while its report actions are resolved live-first (matching the getPolicyFromSearchSnapshot convention) — mixed provenance when a report is cached. It's intentional and the inline comments explain the reasoning, so no change needed; just noting it collapses to snapshot-only for the never-opened case this targets, which is the important one.

LGTM once (1) and (2) are addressed/confirmed.


view run

@VickyStash

Copy link
Copy Markdown
Contributor Author

I still need to address Melvin's first comment and the Codex comment (they are related). I have some doubts regarding it, maybe for reject flow I'll just add Log for now to monitor and won't change anything to not cause side issues. I'll focus on it tomorrow morning.

@VickyStash

Copy link
Copy Markdown
Contributor Author

@MelvinBot some updates were applied, review

@MelvinBot

Copy link
Copy Markdown
Contributor

Re-review

All three points from my last pass are addressed cleanly. 👍

  • (1) Reject behavior — you reverted the snapshot-first resolution and kept the reject path on live Onyx (allReports), adding a monitoring log when the report is missing. Given your doubts about side effects, gating the change behind data on how often uncached reports actually hit reject is the right conservative call. The revert is complete — SearchRejectReasonPage is back to positional args, the RejectMoneyRequestsOnSearchParams type and the useSearchResultsContext/searchData plumbing are fully removed, and Log is already imported. Just flagging that this leaves the original reject edge case (uncached report → transactionCount 0 / policyID undefined → one-by-one instead of the whole-report path) open by design, now observable via the [BulkReject] log.
  • (2) Test coverage — the new delete test exercises exactly the regression: report + report actions only in the snapshot, and asserts deleteAppReport still receives both via the snapshot-first fallback. Un-mocking the two real helpers is the right approach.
  • (3) DM chat lookup — areAllTransactionsFromDMReports now resolves the chat report snapshot-first via getReportOrDraftReport, matching the iouReport lookup right above it.

Two small, optional notes:

  • The [BulkReject] line uses Log.info(..., false, ...), which is server-only (not in the client log window) — good for passive monitoring. If you want it to surface more readily when you go looking, Log.hmmm would tag it as a warning; info is fine if the intent is a quiet counter.
  • The delete test covers the whole-report path (else branch); the isExpenseReportType call site shares the same resolution logic, so no need for a second test unless you want belt-and-suspenders.

LGTM. Reject edge case can be a fast-follow once the log tells you whether it's worth the risk.


view run

@VickyStash

Copy link
Copy Markdown
Contributor Author

@shubham1206agra Let me know what you think!

@mountiny

Copy link
Copy Markdown
Contributor

@shubham1206agra please prioritize this

@mountiny

mountiny commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@shubham1206agra please continue

@VickyStash

Copy link
Copy Markdown
Contributor Author

@shubham1206agra kind bump ^^

@VickyStash

Copy link
Copy Markdown
Contributor Author

@shubham1206agra I'll be OOO next week, if possible, let's try to finalize review today

@shubham1206agra

Copy link
Copy Markdown
Contributor

@codex review

Comment thread src/hooks/useSearchBulkActions.ts Resolved

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f95549a6b8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread src/hooks/useSearchBulkActions.ts Resolved
@shubham1206agra

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-09-04.at.7.12.12.PM.mov

@melvin-bot
melvin-bot Bot requested a review from mountiny September 4, 2026 13:46
@VickyStash

Copy link
Copy Markdown
Contributor Author

I'll be OOO next week, back on September 14 🌴
If any action is needed before that, please reach to @TMisiukiewicz so he can help to find someone

@mountiny
mountiny merged commit 2d05ebd into Expensify:main Sep 8, 2026
34 of 35 checks passed
@github-actions

github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

🚧 mountiny has triggered a test Expensify/App build. You can view the workflow run here.

@OSBotify

OSBotify commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@OSBotify

OSBotify commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/mountiny in version: 9.4.74-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

MelvinBot commented Sep 8, 2026 •

Copy link
Copy Markdown
Contributor

🤖 No help site changes are required for this PR. I did not create a docs PR.

Why: this is an internal bug fix with no user-facing change. It changes how Search bulk Delete and Reject resolve a report — preferring the search snapshot over the Onyx report_ collection — so rows that were silently skipped now delete as expected.

What I checked

The diff touches three files, none of which add, rename, or remove any user-facing feature, tab, setting, or button label:

The help site already documents the behavior this PR restores. Getting Started with the Spend Page tells members to select rows with checkboxes and use the bulk Delete action. That text was already correct — the bug meant it sometimes didn't work, not that the documentation was wrong. Fixing the code makes the existing article accurate again, so nothing needs rewording.

I also scanned the rest of docs/articles for bulk actions and report deletion, including Expense and Report Actions and How to Delete Expenses. None of them describe the Onyx caching behavior this PR changes.

@VickyStash, since no documentation update is needed, there is no linked help site PR to review. If you think an article should still be updated, reply with @MelvinBot and what you'd like documented, and I'll open the draft PR.


view run · view recording

@OSBotify

OSBotify commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.4.74-2 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants